Right now Marionette tests are only run for ASAN builds but miss TSAN. By inspecting the YAML definition I cannot see why:
https://searchfox.org/mozilla-central/source/taskcluster/kinds/test/marionette.yml

Maybe it requires some setting outside of that specific file?

these tests timeout after 90 minutes:
https://treeherder.mozilla.org/jobs?repo=try&revision=5a60e3051b14a49884920af7f5f9648a6330bdbf

we might want to wait until we can chunk the tests.

Sounds fine. Marking bug 1916456 as dependency.

Also please note that the 2 perma failing restart tests (that would have to be fixed first as well) are causing an extra 16min delay! I should take a look at those first as well. Not sure if they are actually based on the same underlying issue. I would have to test, but this won't happen this week.

https://treeherder.mozilla.org/logviewer?job_id=472911439&repo=try&lineNumber=60738
https://treeherder.mozilla.org/logviewer?job_id=472911439&repo=try&lineNumber=61353

this didn't work as well as I would have liked:
https://treeherder.mozilla.org/jobs?repo=try&revision=a73e75b536b03a62cd73b4364c9e46531a1d115e

first 2 chunks barely ran anything, and the 3rd chunk ran too much and hit the time limit. more work when I am back from PTO

The tricky part are the restart tests! Each and every shutdown and startup of Firefox takes a good amount of time. If we have trouble to balance out between the different chunks I can expect more failures in the future if more of such tests are getting added.

TSAN builds are slow as well. So we might need bug 1921411 resolved first too.

Backed out for causing tsan marionette failures.

• Backout link
• Push with failures
• Failure Log
• Failure line: SUMMARY: ThreadSanitizer: data race /builds/worker/checkouts/gecko/toolkit/xre/ProfileReset.h:72:35 in ProfileResetCleanupAsyncTask::Run()

thanks, this appears to be something tsan is good at catching, I filed a bug just so I can move forward with this and ideally the tsan race will get fixed soon.

Joel, a patch is already attached on bug 1925378 so I would prefer to actually wait with landing the patch on this bug until the bug is fixed.

Bug 1925378 is fixed now. So we can try to land the patch again, right?

https://hg.mozilla.org/mozilla-central/rev/2be4fadbf41d